<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0"></meta>
    
  </head>

  <body>
  <div>
    
    <div ng-include="headerInclude"></div>
    <div ng-controller="Apiman.ApiOverviewController" class="page container" data-field="page" ng-cloak="" ng-show="pageState == 'loaded'">
      <div ng-include="'plugins/api-manager/html/api/api_bc.include'"></div>
      <!-- Entity Summary Row -->
      <div ng-include="'plugins/api-manager/html/api/api_entity.include'"></div>

      <!-- Navigation + Content Row -->
      <div class="row">
        <!-- Left hand nav -->
        <div ng-include="'plugins/api-manager/html/api/api_tabs.include'"></div>
        <!-- /Left hand nav -->

        <!-- Content -->
        <div class="col-md-10 apiman-entity-content apiman-entity-overview">
          <!-- Content Summary -->
          <div class="col-md-12">
            <h1 apiman-i18n-key="api-details">API Details</h1>
            <p apiman-i18n-key="api-overview.api-description">
              This is the API details page.  Use this page to modify the meta-data, plans, and 
              policies for the API.  There is no need to follow the tabs in order, but note that
              you will need to fill out a minimum amount of data before the API can be published
              to the Gateway.  In particular, the Implementation and Plans tabs are important (more
              information below).
            </p>
            
            <h2 apiman-i18n-key="impl">Implementation</h2>
            <p apiman-i18n-key="api-overview.impl-description">
              The 'Implementation' tab is where you go to configure the details of the real API
              being managed.  This is where you tell apiman where the API is, so that we can 
              actually invoke it at runtime.
            </p>
            
            <h2 apiman-i18n-key="definition">Definition</h2>
            <p apiman-i18n-key="api-overview.definition-description">
              The 'Definition' tab allows you to configure an optional API Definition document
              for your API.  A API Definition is a detailed description of the capabilities
              of your API (operation names, http verbs, data models).  For example, you might
              add a Swagger spec document as your API Definition.
            </p>

            <h2 apiman-i18n-key="plans">Plans</h2>
            <p apiman-i18n-key="api-overview.plans-description">
              The 'Plans' tab is used to configure which Plans (already defined in the Organization)
              are available when a Client App wishes to create an API Contract with this 
              API.  Optionally, an API can also be marked as "Public", which means that no
              API Contract is required (the API can be invoked without sending an API Key).
            </p>
            
            <h2 apiman-i18n-key="policies">Policies</h2>
            <p apiman-i18n-key="api-overview.policies-description">
              The 'Policies' tab is where you go if you wish to configure any policies that should
              be enforced for *all* requests to the API, regardless of which user, Client App,
              or Plan is being used.  In other words, API-level policies.
            </p>
            
            <h2 apiman-i18n-key="contracts">Contracts</h2>
            <p apiman-i18n-key="api-overview.contracts-description">
              The 'Contracts' tab will show a table of all Client Apps that have created API
              Contracts to this API.  In other words, it shows all of the registered 
              consumers of the API.  Note that if the API is marked as "Public", this tab
              will likely be empty.
            </p>

            <h2 apiman-i18n-key="endpoint">Endpoint</h2>
            <p apiman-i18n-key="api-overview.endpoint-description">
              The 'Endpoint' tab will show you information about how to invoke the API once
              it is published to the API Gateway.
            </p>

            <h2 apiman-i18n-key="activity">Activity</h2>
            <p apiman-i18n-key="api-overview.activity-description">
              The 'Activity' tab shows a history of all the changes made to the API.  Essentially
              it is an audit log.
            </p>
            
          </div>
          <!-- /Content Summary -->
          
        </div>
        <!-- /Content -->
      </div>
    </div> <!-- /container -->
  </div>
  </body>
</html>
